-
Notifications
You must be signed in to change notification settings - Fork 0
Adds hardhat-deploy scripts for proxy contracts #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, can we do the hardhat-verify as well? I realize that it's going to be common to verify the combinator once deployed and we should support that (and document).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw. don't forget to change the PR branch to main.
d992e9c
to
a0a65c3
Compare
c3c7e24
to
20c1c6c
Compare
20c1c6c
to
f9a155d
Compare
7e85928
to
8bb04bb
Compare
86fbafc
to
abeb310
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove all of the stuff relating to the Morpho deployment and only leave the stuff for proxies. Otherwise LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can omit this. The repo only needs the proxy combinators, similarly for the interface, deployment script and deployment JSON files.
|
||
const isLocalNetwork = network.name === 'hardhat' || network.name === 'localhost'; | ||
|
||
const confirmations = isLocalNetwork ? 1 : 5; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't 5 a bit too much?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On some chains 5 confirmations might take quite a long time but on most it won't. This number was suggested to me by the hardhat-deploy plugin when deploying against ethereum-sepolia-testnet and usually 5 confirmations is a common safety measure for non-local deployments, balancing speed with protection against blockchain reorganizations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the purpose of this file? Imo we shouldn't store the deployment files (because arguably they are going to be deployed by third parties and having the deployments stored doesn't make sense for Api3).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because of Morpho I thought that we would be doing the deployments for them. I've remove everything to deployments and Morpho tho 👍🏻
No description provided.